Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1363

reference: 203-tree-1
name: 1363
tree-preservation-order: undefined
203-tpo-1
uprn
address-text
point: POINT (-1.026809 50.864710)
geometry: MULTIPOLYGON (((-1.026739 50.864702,-1.026742 50.864716,-1.026752 50.864729,-1.026767 50.864739,-1.026787 50.864745,-1.026809 50.864748,-1.026831 50.864746,-1.026851 50.864740,-1.026867 50.864730,-1.026877 50.864717,-1.026881 50.864703,-1.026877 50.864690,-1.026868 50.864677,-1.026852 50.864667,-1.026832 50.864660,-1.026811 50.864658,-1.026789 50.864660,-1.026769 50.864666,-1.026753 50.864676,-1.026742 50.864688,-1.026739 50.864702)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL